home *** CD-ROM | disk | FTP | other *** search
- Path: cs.uwa.edu.au!jasonb
- From: jasonb@cs.uwa.edu.au (Jason S Birch)
- Newsgroups: comp.sys.amiga.misc
- Subject: Re: MUI 3.2
- Date: 7 Feb 96 16:37:04 GMT
- Organization: The University of Western Australia
- Message-ID: <jasonb.823711024@cs.uwa.edu.au>
- References: <3116bca3@karkis.canit.se>
- NNTP-Posting-Host: decadence.cs.uwa.oz.au
- X-Newsreader: NN version 6.5.0 #3 (NOV)
-
- bornhall@karkis.canit.se (Peter Bornhall) writes:
- > Same here, BUT; I didn't WANT that MUI: assign, alas I removed it and tried to
- >direct the MUI (we're talking 2.3 now) prefs program to a drawer I created in
- >SYS:Classes (called MUI) instead. But, as far as I can remember, the MUI prefs
- >program STILL saved the prefs with references to MUI:. So eventually I had to
- >manually edit the prefs file to fix this, IMO, bug.
-
- I successfully removed MUI 2.3's dependence on the MUI: assign simply
- by removing references to patterns and images relative to it. Why on
- earth would you have to manually edit the prefs file?
-
- > tai> Since MUI has so many options, it comes with many files (libs, images
- > tai> etc.).
- > tai> You don't want to have them all in a public directory like LIBS:.
-
- > Why not? That's what those drawers are there for! And a power-user can
- >always prevent 3rd-party libs from clogging up the system libs for example.
- >And the MUI imagery, wouldn't that fit perfectly in SYS:Classes/Images or
- >something similar?
-
- It used to. People complained about their normal public directories
- getting clogged, and having the libraries scattered all over the place.
- A power user should have no difficulty moving them there if they want to.
-
- > /\ \// Peter Bornhall bornhall@karkis.canit.se
-
- --
- Jason S Birch ,-_|\ email: jasonb@cs.uwa.edu.au
- Department of Computer Science / \ Tel (work): +61 9 380 1840
- The University of Western Australia *_.-._/ Fax (work): +61 9 380 1089
- Nedlands W. Australia 6907 v Tel (home): +61 9 386 8630
-